Motivation

When setting up a TrustZone Secure world on Cortex-M33 (ARMv8-M), three things need to happen before jumping to the Non-Secure application:

1. Allow Non-Secure code to use the FPU — requires writing SCB->NSACR bits 10–11 (CP10/CP11).
2. Route peripheral interrupts to the Non-Secure world — requires writing NVIC->ITNS[n].
3. Optionally query whether a given interrupt is already routed to Non-Secure.

Neither SCB->NSACR nor typed NVIC->ITNS accessors are currently exposed by this crate, forcing users to fall back to raw pointer writes against magic addresses. This PR closes that gap.

Changes

scb.rs

• Add pub nsacr: RW<u32> to RegisterBlock, gated #[cfg(armv8m)], at the correct offset (CPACR + 4 = 0xE000_ED8C).
• Add an #[cfg(armv8m)] impl SCB block with three methods:
  • enable_nonsecure_fpu(&mut self) — sets NSACR bits 10–11.
  • disable_nonsecure_fpu(&mut self) — clears them.
  • is_nonsecure_fpu_enabled() -> bool — reads the current state.

nvic.rs

The itns: [RW<u32>; 16] field already exists (added in #580) but had no typed methods. Three #[cfg(armv8m)] methods are added to impl NVIC:

• unsafe route_to_nonsecure<I: InterruptNumber>(interrupt: I) — sets the ITNS bit.
• unsafe route_to_secure<I: InterruptNumber>(interrupt: I) — clears it.
• is_routed_to_nonsecure<I: InterruptNumber>(interrupt: I) -> bool — reads it.

The unsafe on the mutating methods matches the precedent set by unmask — incorrect routing can violate security invariants.

test.rs

• Address assertions for nvic.itns (0xE000_E380) and nvic.itns[1] (0xE000_E384), gated #[cfg(armv8m)].
• Address assertion for scb.nsacr (0xE000_ED8C), gated #[cfg(armv8m)].

Testing

cargo test -p cortex-m --features std --lib passes (11/11). The new #[cfg(armv8m)] assertions are verified when targeting thumbv8m.main-none-eabihf. The pre-existing macros::CPASS_ATTR doctest failure is a macOS LLVM section-specifier issue unrelated to this PR.